home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
ftp.cs.arizona.edu
/
ftp.cs.arizona.edu.tar
/
ftp.cs.arizona.edu
/
icon
/
newsgrp
/
group94a.txt
/
000008_icon-group-sender _Thu Jan 6 21:35:51 1994.msg
< prev
next >
Wrap
Internet Message Format
|
1994-08-19
|
1KB
Received: by cheltenham.cs.arizona.edu; Mon, 10 Jan 1994 12:06:01 MST
Date: 6 Jan 94 21:35:51 GMT
From: walter!flaubert!norman@rutgers.edu (Norman Ramsey)
Organization: Bellcore, Morristown NJ
Subject: Icon and sockets
Message-Id: <CJ89Br.BpG@walter.bellcore.com>
References: <CJ7nLJ.DL6@walter.bellcore.com>
Sender: icon-group-request@cs.arizona.edu
To: icon-group@cs.arizona.edu
Status: R
Errors-To: icon-group-errors@cs.arizona.edu
In article <CJ7nLJ.DL6@walter.bellcore.com>,
Darren New <dnew@thumper.bellcore.com> wrote:
>You can delete, unfortunately, easy low-level nonportable access to OS
>features. It's non-trivial to use sockets, for example, from inside
>Icon, I've found.
Yes, and it's a disappointment. I had the idea of trying
socket := open("telnet myhost 119", "bp")
on a Unix host to see if I could write network clients that way, but I
haven't actually gotten around to it yet. If anyone gets something
similar to work, I would enjoy hearing about it.
To write servers, the best alternative may be to write a C program
that uses accept(2) and then forks an Icon program once a connection
is established.
Norman